Systems and methods for data cleansing such as for optimizing clinical scheduling

ABSTRACT

A scheduling system and method for data cleansing may be used to optimize clinical scheduling. The present disclosure describes receiving clinical record data, in an agnostic manner, from a system including a source scheduling database containing the clinical record data; mapping the clinical record data to a desired format; conforming the clinical record data to standardized scheduling elements of the scheduling system; cleansing, in a manner configurable by a user, the clinical record data to purge portions of the clinical record data; providing the clinical record data to an optimization engine for optimization of the clinical record data; optimizing the clinical record data by applying configurable logic to the clinical record data; and uploading one or more newly defined optimized scheduling templates via an outbound connection back to the scheduling system.

FIELD OF THE DISCLOSURE

This disclosure relates to scheduling systems and methods for data cleansing to optimize clinical scheduling.

BACKGROUND

Scheduling systems are known. Scheduling systems allow professionals to manage scheduling appointments and bookings, among other things. Technical problems are inherent within these current computer systems (e.g., scheduling systems or other systems). For example, when receiving input (e.g., clinical record data or other types of data) from scheduling databases, existing scheduling systems include scheduling products that rely on custom interfaces and application programming interfaces (APIs) for each electronic record the scheduling systems receive as input. An API is code that allows, for example, two software programs to communicate with each other. An API may be used for one or more web-based systems, operating systems, and/or database systems. One example of such input would be electronic medical records (EMRs). Without custom interfaces and APIs, current scheduling systems would only be able to operate on input from certain (or no) scheduling databases. Many scheduling systems are deficient or absent in their capabilities to optimize the scheduling of critical resources. This causes wasted opportunities and may contribute to delayed subject care.

SUMMARY

One aspect of the disclosure may relate to a scheduling system configured for data cleansing to optimize clinical scheduling. The scheduling system may include one or more hardware processors and/or other components. The one or more hardware processors may be configured by machine-readable instructions to receive clinical record data, in an agnostic manner (discussed herein), from a system including a source scheduling database containing the clinical record data. The clinical record data may be mapped to a desired format that may include a plurality of fields. The scheduling system may conform the clinical record data to standardized scheduling elements of the scheduling system. This may be accomplished by parsing the clinical record data. The parsing may include reformatting the clinical record data by assigning portions of the data to appropriate fields.

In addition, one or more hardware processors may be configured to cleanse, in a manner configurable by a user, the clinical record data to purge portions of the clinical record data related to one or more of data errors, data artifacts, business logic, and/or other items. The clinical record data may be provided to an optimization engine for optimization of the clinical record data. Further, the clinical record data may be optimized by applying configurable logic to the clinical record data. Doing so may provide one or more newly defined optimized scheduling templates that configure defined resources such as one or more of providers, rooms, equipment such as X-ray machines and/or EKG monitors for optimal usage of time, where resource availability is matched with customized variables. The customized variables may include one or more of visit complexity, average visit length, number of exam rooms, provider preference, non-physician resources, and/or other information. One or more newly defined optimized scheduling templates may be uploaded via an outbound connection back to the scheduling system.

Another aspect of the disclosure may relate to a method for data cleansing to optimize clinical scheduling. The scheduling method may be performed by one or more hardware processors and/or other components. The one or more hardware processors may be configured by machine-readable instructions to receive clinical record data, in an agnostic manner, from a system including a source scheduling database containing the clinical record data. The clinical record data may be mapped to a desired format that may include a plurality of fields. The scheduling system may conform the clinical record data to standardized scheduling elements of the scheduling system. This may be accomplished by parsing the clinical record data. The parsing may include reformatting the clinical record data by assigning portions of the data to appropriate fields.

In addition, one or more hardware processors may be configured to cleanse, in a manner configurable by a user, the clinical record data to purge portions of the clinical record data related to one or more of data errors, data artifacts, business logic, and/or other items. The clinical record data may be provided to an optimization engine for optimization of the clinical record data. Further, the clinical record data may be optimized by applying configurable logic to the clinical record data. Doing so may provide one or more newly defined optimized scheduling templates that configure one or both of providers and rooms for optimal usage of time, where provider availability is matched with customized variables. The customized variables may include one or more of visit complexity, average visit length, number of exam rooms, provider preference, non-physician resources, and/or other information. One or more newly defined optimized scheduling templates may be uploaded via an outbound connection back to the scheduling system.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system for data cleansing to optimize clinical scheduling, in accordance with one or more implementations.

FIG. 2 illustrates a data cleansing structure, in accordance with one or more implementations.

FIG. 3 illustrates a method for data cleansing to optimize clinical scheduling, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a scheduling system 100 configured for data cleansing to optimize clinical scheduling system, in accordance with one or more implementations. In some implementations, scheduling system 100 may include one or more servers 102. The server(s) 102 may be configured to communicate with one or more computing platforms 104 according to client/server architecture, a peer-to-peer architecture, and/or other architectures. The users may access system 100 via computing platform(s) 104. A platform is an underlying computer system on which application programs can run.

The server(s) 102 may be configured to execute machine-readable instructions 106. The machine-readable instructions 106 may include one or more of a mapping component 106, a conforming component 110, a cleansing component 112, an optimizing component 114, and/or other machine-readable instruction components.

The machine-readable instructions 106 may be executable to provide a subject scheduling optimization suite that improves schedule utilization and subject flow. Exemplary implementations of the present technology may provide an intelligent scheduling platform that is effective in a variety of subject clinic settings. Exemplary implementations of the present technology include one or more of an inbound connection to any scheduling database, a standardized format of universal data elements from scheduling data, cleansing component 112 that purges data, such as for example historical data including data errors, optimization component 114 that leverages legacy data to be analyzed with configurable logic and provide optimized scheduling templates, an outbound connection back to the scheduling system to upload newly defined scheduling templates, and/or other components.

As mentioned herein, exemplary implementations of the present technology may include cleansing component 112. As opposed to other scheduling products that rely on custom interface and API work for each electronic medical record, exemplary implementations of the present technology may include a platform configured to force data from other systems to be conformed to its own standardized scheduling elements. This allows exemplary implementations of the present technology to be compatible with any electronic medical record with significantly less work.

Exemplary implementations of the present technology may provide a platform built on, for example, a star schema extensible framework. The star schema extensible framework may include one or more fact tables referencing any number of dimension tables. The fact tables may include one or more of numerical values or information regarding where descriptive information is kept, and/or other information. The dimension tables may include one or more of records with attributes to describe the fact data, and/or other information. A central, or primary, fact table may include standardized scheduling elements including one or more of appointment information, subject and provider keys, scheduling start and end times, and/or other information. According to some implementations, there is only one primary fact table in system 100. The primary fact table may sit at the center of the scheduling star schema of scheduling system 100. The primary fact table contains the relevant primary scheduling data for system 100. Within this primary fact table are keys that join to other tables that provide dimensional information.

In some exemplary implementations, the primary fact table may contain the fact that subject Joe Smith had an appointment on Wednesday, Mar. 23, 2016 at 2:00 p.m. Relevant information related to Joe Smith's demographic information is not typically stored in this primary fact table; however, in some implementations it may be. Typically, the relevant information would instead be stored in a separate table and keyed to the primary fact table by a primary field such as a patient ID (or subject ID). Thus, Joe Smith's scheduling information is keyed and joined to his demographic information within the scheduling model.

In some implementations according to the present technology, a standardized central fact table may be created that has conformed dimensions. This standardized central fact table may be assigned a logical name, such as, for example, F_Schedule_Retro. The name F_Schedule_Retro refers to the fact legacy retrospective table of schedule data. Standardized dimensional tables may be built with detail information such as appointment outcome information including one or more of appointment statuses, actual start times, actual end times, and/or other information. Subject and provider dimensional tables may be included with details that may include one or more of subject demographics, provider specialty information, and/or other information.

FIG. 2 illustrates a data cleansing structure 200, in accordance with one or more implementations. Arrows in FIG. 2 show an exemplary flow of data through data cleansing structure 200. Clinical record data may be received from a source scheduling database 202, such as clinical database 116 of FIG. 1. The clinical record data may be extracted via one or more of an object linking and embedding database (OLEDB), an open database connectivity (ODBC) system, an API, and/or other techniques. OLEDB and ODBC connectors are standard database connectors commonly used to access data from Microsoft structured query language (SQL) or Oracle databases. These are the most common databases used for legacy scheduling data. However, it is contemplated that other types of databases may be used in various implementations according to the present technology. For non-standard databases, APIs or other connectors may be used to extract data and conformed to the products standard.

Once this data is in the desired format, a cleansing component 112 may perform user configurable cleansing actions. Examples of these actions may include the cleansing of data errors including rows of data missing documentation, to data artifacts in the form of data for a clinic that no longer exists. Business logic like ignoring all data from Thursdays, for example, may be performed at this stage in cleansing component 112.

Source scheduling database 202 may be communicatively coupled with platform 204 of the present disclosure. EHR live component 206 may also be communicatively coupled with platform 204. Platform 202 may be communicatively coupled with cleansing component 112, or may include cleansing component 112. Thus, source scheduling database 202 and EHR live component 206 may be communicatively coupled with cleansing component 112. In some implementations, components such as EHR live component 206 may be directly connected to cleansing component 112. Ergo, the present technology may advantageously allow for being able to directly pull data (e.g., clinical record data) from a live system (EHR live component 206). This technique allows for taking care of real-time or near real-time scheduling needs. One or more of platform 204, cleansing component 112, and/or other components may be communicatively coupled with optimizing component 114.

Clinical record data that is excluded from optimization component 114 may be stored for analytics and reporting, allowing insight into the types and amounts of data that are being excluded from analysis (metadata). Data that is cleansed may be fed to optimization component 114 for further analysis (machine learning).

In some implementations, platform 204 may be extensible so that inclusion of new data elements may be accomplished quickly with little added overhead. Newly requested elements may be created and then mapped from source data, via mapping component 108, and be run through optimizing component 114, leveraging configurable cleansing logic.

In some implementations, platform 204 may require data to be in the format shown in Table 1, in accordance with one or more implementations. Note that instances of the term “patient” in the tables (e.g., PatientKey in Table1) could be generally though of as “subject” (e.g., SubjectKey). Table 1 is the central fact table, and resides at the center of the model for the process in some implementations.

TABLE 1 (Desired Format) PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd

A prospective organization may have data from their electronic record in the format shown in one or both of Table 2, Table 3, or another format, in accordance with one or more implementations.

TABLE 2 (Appointment Scheduled Table) APPT_KEY PAT_ID APPT_PROV_ID DEPT_ID APPT_SCHED_S APPT_SCHED_E

TABLE 3 (Appointment Actual Table) APPT_KEY APPT_START APPT_END

The prospective organization's data may be extracted and mapped to the desired format, as shown in Table 4, in accordance with one or more implementations.

TABLE 4 PAT_ID APPT_PROV_ID DEPT_ID APPT_SCHED_S APPT_SCHED_E APPT_START APPT_END

The data map may appear as shown in Table 5, in accordance with one or more implementations.

TABLE 5 PAT_ID APPT_PROV_ID DEPT_ID APPT_SCHED_S APPT_SCHED_E APPT_START APPT_END PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd

There are several problems inherent to computer systems that are addressed by the present technology. Once within platform 204, cleansing component 112 may begin its work. Cleansing component 112 may provide standard cleansing functions to, for example, ignore data that is incomplete. In some implementations, source scheduling database 202 may be a legacy system. A legacy system includes one or more of an old method, technology, outdated computer system, application program, and/or other system. Referencing a system as “legacy” often implies that the system is out of date or in need of replacement. It is common to refer to a system that has been turned off already, but for which the data is still being used for analytics, as a legacy system.

Advantageously, implementations according to the present technology work with any source scheduling database 202, including legacy systems, without the need for various APIs or the like. Advantageously, since scheduling system 100 works with any existing electronic medical record, this enables clinics or other entities to maximize subject flow with existing staff and facilities. A further advantage provided is the synchronization of data from legacy systems, which is something that typically is not done currently. This paradigm provides a holistic picture of legacy scheduling data instead of a piecemeal picture based on an origin of a system. Clinics have several challenges when faced with limited personnel and resources that continue to diminish in the increasingly difficult healthcare environment. Many providers struggle to find the balance between operational efficiency that requires possible double-booking (or triple-booking etc.) of subjects to accommodate potential no-shows and subject satisfaction that might suffer from resulting longer wait-times or decreased schedule availability. Without the proper clinical intelligence, both subjects and operations suffer. Implementations according to the present technology solve these technical problems. A data-driven approach is provided to optimize clinic scheduling. Provider satisfaction is improved by normalizing subject flow and aligning clinic operations. Subject satisfaction is improved by reducing wait times and enhancing appointment availability. Efficiency is improved by generating clinic performance metrics and increasing productivity and asset utilization. Staff may be happier due to more efficient and accurate scheduling. Subjects may be happier due to decreased wait times and optimized staff availability. Better operational effectiveness may translate to improved revenue and resource forecasting.

Appointment information such as, for example, legacy appointment information (from a legacy system) that is missing actual start or end times may be ignored so as not to impact analysis and generation of scheduling templates downstream. Some implementations may be configured to allow custom configuration to cleanse data from inclusion into optimization component 114 for other reasons.

In some exemplary implementations, a prospective organization may desire to ignore all appointments completed by “Dr. Smith” who retired earlier in the summer. Dr. Smith's Provider Key may be 1131, for example.

A portion of the prospective organization's data may be extracted and conformed to look as shown in Table 6.

TABLE 6 PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd 100125 1131 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:09 Jun. 8, 2015 8:34 100159 1125 101 Jun. 8, 2015 8:30 Jun. 8, 2015 9:30 Jun. 8, 2015 9:50 101123 1189 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:03 Jun. 8, 2015 9:37 111346 1167 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:32 100583 1192 101 Jun. 8, 2015 8:00 Jun. 8, 2015 9:00 Jun. 8, 2015 8:01 Jun. 8, 2015 9:20 107888 1158 101 Jun. 8, 2015 11:00 Jun. 8, 2015 11:30 Jun. 8, 2015 11:13 Jun. 8, 2015 11:50 113689 1136 101 Jun. 8, 2015 10:00 Jun. 8, 2015 11:00 Jun. 8, 2015 10:07 Jun. 8, 2015 10:44 123482 1131 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 8:55 Jun. 8, 2015 9:15 186321 1258 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:22 Jun. 8, 2015 8:48 100931 1479 101 Jun. 8, 2015 9:00 Jun. 8, 2015 10:00 Jun. 8, 2015 9:13 Jun. 8, 2015 10:01 103546 1189 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:01 161001 1158 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30

In some implementations, cleansing component 112 may address common data errors such as, for example, data with missing information (see Table 7).

TABLE 7 PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd 100125 1131 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:09 Jun. 8, 2015 8:34

101123 1189 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:03 Jun. 8, 2015 9:37 111346 1167 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:32 100583 1192 101 Jun. 8, 2015 8:00 Jun. 8, 2015 9:00 Jun. 8, 2015 8:01 Jun. 8, 2015 9:20 107888 1158 101 Jun. 8, 2015 11:00 Jun. 8, 2015 11:30 Jun. 8, 2015 11:13 Jun. 8, 2015 11:50 113689 1136 101 Jun. 8, 2015 10:00 Jun. 8, 2015 11:00 Jun. 8, 2015 10:07 Jun. 8, 2015 10:44 123482 1131 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 8:55 Jun. 8, 2015 9:15 186321 1258 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:22 Jun. 8, 2015 8:48 100931 1479 101 Jun. 8, 2015 9:00 Jun. 8, 2015 10:00 Jun. 8, 2015 9:13 Jun. 8, 2015 10:01

161001 1158 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30

The appointments highlighted in bold/italics may be removed from data that will be passed on to optimization component 114. The prospective organization may request that Dr. Smith (having provider key 1131) be removed from inclusion in analysis.

These lines may be cleansed from inclusion in optimization component 114 (see Table 8).

TABLE 8 PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd

101123 1189 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:03 Jun. 8, 2015 9:37 111346 1167 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:32 100583 1192 101 Jun. 8, 2015 8:00 Jun. 8, 2015 9:00 Jun. 8, 2015 8:01 Jun. 8, 2015 9:20 107888 1158 101 Jun. 8, 2015 11:00 Jun. 8, 2015 11:30 Jun. 8, 2015 11:13 Jun. 8, 2015 11:50 113689 1136 101 Jun. 8, 2015 10:00 Jun. 8, 2015 11:00 Jun. 8, 2015 10:07 Jun. 8, 2015 10:44

186321 1258 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:22 Jun. 8, 2015 8:48 100931 1479 101 Jun. 8, 2015 9:00 Jun. 8, 2015 10:00 Jun. 8, 2015 9:13 Jun. 8, 2015 10:01

161001 1158 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30

The result is shown in Table 9, in accordance with one or more implementations.

TABLE 9 PatientKey ProviderKey ClinicKey ScheduleStart ScheduleEnd ActualStart ActualEnd 101123 1189 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:03 Jun. 8, 2015 9:37 111346 1167 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:32 100583 1192 101 Jun. 8, 2015 8:00 Jun. 8, 2015 9:00 Jun. 8, 2015 8:01 Jun. 8, 2015 9:20 107888 1158 101 Jun. 8, 2015 11:00 Jun. 8, 2015 11:30 Jun. 8, 2015 11:13 Jun. 8, 2015 11:50 113689 1136 101 Jun. 8, 2015 10:00 Jun. 8, 2015 11:00 Jun. 8, 2015 10:07 Jun. 8, 2015 10:44 186321 1258 101 Jun. 8, 2015 8:00 Jun. 8, 2015 8:30 Jun. 8, 2015 8:22 Jun. 8, 2015 8:48 100931 1479 101 Jun. 8, 2015 9:00 Jun. 8, 2015 10:00 Jun. 8, 2015 9:13 Jun. 8, 2015 10:01 161001 1158 101 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30 Jun. 8, 2015 9:00 Jun. 8, 2015 9:30

It is envisioned that periodic (e.g., weekly etc.) dashboard report customized templates may be provided.

Returning to FIG. 1, in some implementations, server(s) 102, computing platform(s) 104, and/or external resources 118 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, computing platform(s) 104, and/or external resources 118 may be operatively linked via some other communication media.

A given computing platform 104 may include one or more processors configured to execute machine-readable instructions. The machine-readable instructions may be configured to enable an expert or user associated with the given computing platform 104 to interface with system 100 and/or external resources 130, and/or provide other functionality attributed herein to computing platform(s) 104. By way of non-limiting example, the given computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources 118 may include sources of information, hosts and/or providers of block chain environments outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 118 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 122, one or more processors 120, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 122 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 122 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 122 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 122 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 122 may store software algorithms, information determined by processor(s) 120, information received from server(s) 102, information received from computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 120 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 120 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 120 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 120 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 120 may represent processing functionality of a plurality of devices operating in coordination. The processor(s) 134 may be configured to execute machine-readable instruction components 108, 110, 112, 114, and/or other machine-readable instruction components. Processor(s) 120 may be configured to execute machine-readable instruction components 108, 110, 112, 114, and/or other machine-readable instruction components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 120. As used herein, the term “machine-readable instruction component” may refer to any component or set of components that perform the functionality attributed to the machine-readable instruction component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although machine-readable instruction components 108, 110, 112, 114 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 120 includes multiple processing units, one or more of machine-readable instruction components 108, 110, 112, and/or 114 may be implemented remotely from the other machine-readable instruction components. The description of the functionality provided by the different machine-readable instruction components 108, 110, 112, and/or 114 described herein is for illustrative purposes, and is not intended to be limiting, as any of machine-readable instruction components 108, 110, 112, and/or 114 may provide more or less functionality than is described. For example, one or more of machine-readable instruction components 108, 110, 112, and/or 114 may be eliminated, and some or all of its functionality may be provided by other ones of machine-readable instruction components 108, 110, 112, and/or 114. As another example, processor(s) 120 may be configured to execute one or more additional machine-readable instruction components that may perform some or all of the functionality attributed below to one of machine-readable instruction components 108, 110, 112, and/or 114.

FIG. 3 illustrates a method 300 for data cleansing to optimize clinical scheduling, in accordance with one or more implementations. The operations of method 300 presented below are intended to be illustrative. In some implementations, method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 300 are illustrated in FIG. 3 and described below is not intended to be limiting.

In some implementations, one or more operations of method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 300.

At an operation 302, the clinical record data may be received, in an agnostic manner, at platform 204 from a system including a source scheduling database 202 containing clinical record data. In this context, agnostic may refer to something that is generalized so that it is interoperable among various systems. Source scheduling database 202 may be any database, and thus the clinical record data may be received in an agnostic manner.

At an operation 304, clinical record data is mapped to a desired format. The desired format may a plurality of fields.

At an operation 306, the clinical record data is conformed to standardized scheduling elements of the scheduling system by parsing the clinical record data. The parsing may include reformatting the clinical record data by assigning portions of the data to appropriate fields.

At an operation 308, the clinical record data is cleansed, in a manner configurable by a user, to purge portions of the clinical record data related to one or more of data errors, data artifacts, or business logic. By design, platform 204 may allow a rules engine (or rules component) to be used by an end-user to effectively filter out erroneous data. The logic may be designed to exclude data based on user-configured selections depending on on the fact table's dimensions.

For example, “weekday” may be a resultant dimension in the scheduling fact data. A user may want to ignore any instances where Dr. Smith had appointments on Wednesdays since he usually does not work on Wednesdays. In this case, the user may be able to create a rule that says ignore data where Dr. Smith is a provider and the appointment weekday is a Wednesday.

Additionally, for clinics that allow walk-ins for urgent care, unscheduled add-on appointments could muddy data that is based on scheduled appointments being completed. In this case, an end-user would be able to create and apply a rule that states, ignore all data that coincides with appointments that are of type “add-on” or “urgent care.”

At an operation 310, clinical record data is provided to optimizing component 114 for optimization of the clinical record data.

At an operation 312, the clinical record data is optimized by applying configurable logic to the clinical record data in order to provide one or more newly defined optimized scheduling templates that configure one or both of providers and/or rooms for optimal usage of time. Provider availability is matched with customized variables. The customized variables include one or more of visit complexity, average visit length, number of exam rooms, provider preference, non-physician resources, and/or other variables and/or information. Optimization component 114 may also include the ability for system- and user-defined rules to optimize schedules by resource (not just by provider).

In some implementations, the order of priority of rules may be modified in optimization component 114. Thus, if there is ever a conflict in the rules then a rule that is listed first may take precedence.

In one exemplary implementation, data has been cleansed and Dr. Williams desired an optimized schedule. He does not work Wednesday afternoons and he would prefer to take longer appointments Wednesday mornings when he does work. Historical data may show that Dr. Williams averages seven 45-minute appointments per week and three 60-minute appointments per week. The schedule may be blocked off such that Dr. Williams is slated to work from 8:00 a.m. until 12:00 p.m. The ordering of the appointments thus may include assigning the three 60-minute appointments (scheduling his time until 11:00 a.m.), and then attempting to fit in two 45-minute appointments. However, do so would overbook the schedule to 12:30 p.m. instead of the desired time of 12:00 p.m. Instead, system 100 recognizes the hard stop at 12:00 p.m. and inserts three 20-minute appointment blocks.

At an operation 314, one or more newly defined optimized scheduling templates are uploaded via an outbound connection back to scheduling system 100.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation. 

What is claimed is:
 1. A scheduling system configured for data cleansing to optimize clinical scheduling, the system comprising: one or more hardware processors configured by machine-readable instructions to: receive clinical record data, in an agnostic manner, from a system including a source scheduling database containing the clinical record data; map the clinical record data to a desired format, the desired format including a plurality of fields; conform the clinical record data to standardized scheduling elements of the scheduling system by parsing the clinical record data, the parsing including reformatting the clinical record data by assigning portions of the data to appropriate fields; cleanse, in a manner configurable by a user, the clinical record data to purge portions of the clinical record data related to one or more of data errors, data artifacts, or business logic; provide the clinical record data to an optimization engine for optimization of the clinical record data; optimize the clinical record data by applying configurable logic to the clinical record data in order to provide one or more newly defined optimized scheduling templates that configure one or both of providers and rooms for optimal usage of time, where provider availability is matched with customized variables, the customized variables including one or more of visit complexity, average visit length, number of exam rooms, provider preference, or non-physician resources; and upload one or more newly defined optimized scheduling templates via an outbound connection back to the scheduling system.
 2. The system of claim 1, wherein conforming the clinical record data allows the scheduling system to work with any electronic medical record.
 3. The system of claim 1, wherein the one or more hardware processors are further configured by machine-readable instructions to allow a primary fact table of data to be surrounded by dimensional tables, the primary fact table of data including standardized scheduling elements that include one or more of appointment information, subject and provider keys, appointment scheduling start times, or appointment scheduling end times, the dimensional tables including one or more of standardized dimensional tables, subject dimensional tables, or provider dimensional tables.
 4. The system of claim 3, wherein the standardized dimensional tables include detail information that includes one or more of appointment outcome information having appointment statuses, actual appointment start times, or actual appointment end times, and wherein subject and provider dimensional tables include detail information that includes one or both of subject demographics or provider specialty information.
 5. The system of claim 1, wherein the one or more hardware processors are further configured by machine-readable instructions to utilize a star schema extensible framework, the star schema extensible framework including one or more fact tables referencing any number of dimension tables, the fact tables including one or both of numerical values or information regarding where descriptive information is kept, or the dimension tables including records with attributes to describe the fact data.
 6. The system of claim 1, wherein the scheduling system includes subject and provider dimensional tables with details that include one or both of subject demographics or provider specialty information.
 7. The system of claim 1, wherein the one or more hardware processors are further configured by machine-readable instructions to extract data from the source scheduling database via one or more of an OLEDB connection, an ODBC connection, or an API.
 8. The system of claim 1, wherein the one or more hardware processors are further configured by machine-readable instructions to run one or more cleansing functions to ignore one or more of data that is incomplete, appointment information that is missing a start time, or appointment information that is missing an end time.
 9. The system of claim 1, wherein the one or more hardware processors are further configured by machine-readable instructions to cleanse data errors including rows of data missing information.
 10. The system of claim 1, wherein data that is excluded from the optimization engine is stored for analytics and reporting, allowing insight into types and amounts of data that are being excluded from analysis, the insight into types and amounts of data that are being excluded from analysis including one or more of data with missing information, data that is not relevant, data that is incomplete, or data that is erroneous.
 11. A scheduling method configured for data cleansing to optimize clinical scheduling, the method being performed by one or more hardware processors configured by machine-readable instructions, the method comprising: receiving clinical record data, in an agnostic manner, from a system including a source scheduling database containing the clinical record data; mapping the clinical record data to a desired format, the desired format including a plurality of fields; conforming the clinical record data to standardized scheduling elements of the scheduling system by parsing the clinical record data, the parsing including reformatting the clinical record data by assigning portions of the data to appropriate fields; cleansing, in a manner configurable by a user, the clinical record data to purge portions of the clinical record data related to one or more of data errors, data artifacts, or business logic; providing the clinical record data to an optimization engine for optimization of the clinical record data; optimizing the clinical record data by applying configurable logic to the clinical record data in order to provide one or more newly defined optimized scheduling templates that configure one or both of providers and rooms for optimal usage of time, where provider availability is matched with customized variables, the customized variables including one or more of visit complexity, average visit length, number of exam rooms, provider preference, or non-physician resources; and uploading one or more newly defined optimized scheduling templates via an outbound connection back to the scheduling system.
 12. The method of claim 11, wherein conforming the clinical record data allows the scheduling system to work with any electronic medical record.
 13. The method of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to allow a primary fact table of data to be surrounded by dimensional tables, the primary fact table of data including standardized scheduling elements that include one or more of appointment information, subject and provider keys, appointment scheduling start times, or appointment scheduling end times, the dimensional tables including one or more of standardized dimensional tables, subject dimensional tables, or provider dimensional tables.
 14. The method of claim 13, wherein the standardized dimensional tables include detail information that includes one or more of appointment outcome information having appointment statuses, actual appointment start times, or actual appointment end times, and wherein subject and provider dimensional tables include detail information that includes one or both of subject demographics or provider specialty information.
 15. The method of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to utilize a star schema extensible framework, the star schema extensible framework including one or more fact tables referencing any number of dimension tables, the fact tables including one or both of numerical values or information regarding where descriptive information is kept, or the dimension tables including records with attributes to describe the fact data.
 16. The method of claim 11, wherein the scheduling system includes subject and provider dimensional tables with details that include one or both of subject demographics or provider specialty information.
 17. The method of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to extract data from the source scheduling database via one or more of an OLEDB connection, an ODBC connection, or an API.
 18. The method of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to run one or more cleansing functions to ignore one or more of data that is incomplete, appointment information that is missing a start time, or appointment information that is missing an end time.
 19. The method of claim 11, wherein the one or more hardware processors are further configured by machine-readable instructions to cleanse data errors including rows of data missing information.
 20. The method of claim 11, wherein data that is excluded from the optimization engine is stored for analytics and reporting, allowing insight into types and amounts of data that are being excluded from analysis, the insight into types and amounts of data that are being excluded from analysis including one or more of data with missing information, data that is not relevant, data that is incomplete, or data that is erroneous. 